Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0d1d284a9f8a49e3627d5be2df40cf0e09a3a17a3ab214603bade53243319671

Tx prefix hash: 6615fb35f86c242b974f86dd6774a513ec5c60b6fb35ac2a1e9bb0db01cef8a7
Tx public key: 582c2d368308e0fbfad416d6de75a2e9b583ef9c4fda2425f3593341177ed336
Timestamp: 1700471363 Timestamp [UCT]: 2023-11-20 09:09:23 Age [y:d:h:m:s]: 01:062:22:32:35
Block: 895648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306345 RingCT/type: yes/0
Extra: 01582c2d368308e0fbfad416d6de75a2e9b583ef9c4fda2425f3593341177ed33602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.661220584000 dcy

stealth address amount amount idx
00: fe3f7d5aaca8011fa55838a2791cb2848b05f7026fd120f621d85d115e7b0a6d 0.661220584000 1351889 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 895658, "vin": [ { "gen": { "height": 895648 } } ], "vout": [ { "amount": 661220584, "target": { "key": "fe3f7d5aaca8011fa55838a2791cb2848b05f7026fd120f621d85d115e7b0a6d" } } ], "extra": [ 1, 88, 44, 45, 54, 131, 8, 224, 251, 250, 212, 22, 214, 222, 117, 162, 233, 181, 131, 239, 156, 79, 218, 36, 37, 243, 89, 51, 65, 23, 126, 211, 54, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8