Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7282b3f839028f007563549e59051d716b7549d526e53b0c32436df30e69043

Tx prefix hash: f20017bd337497b1085e4bebcd93674b324ba3dda8de27da7dbf49b790afd4a8
Tx public key: 0157237951d9c463c9ca1c17884dce8e4efebc9ce93eba947e7c7ba49e43158b
Timestamp: 1722703933 Timestamp [UCT]: 2024-08-03 16:52:13 Age [y:d:h:m:s]: 00:249:19:50:58
Block: 1079970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178452 RingCT/type: yes/0
Extra: 010157237951d9c463c9ca1c17884dce8e4efebc9ce93eba947e7c7ba49e43158b021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8477d8e5d54a47c0cac4f1f2bd09e4dc8f3d2fff7d77037697632f7c6e540217 0.600000000000 1553147 of 15

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": 1079980, "vin": [ { "gen": { "height": 1079970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8477d8e5d54a47c0cac4f1f2bd09e4dc8f3d2fff7d77037697632f7c6e540217" } } ], "extra": [ 1, 1, 87, 35, 121, 81, 217, 196, 99, 201, 202, 28, 23, 136, 77, 206, 142, 78, 254, 188, 156, 233, 62, 186, 148, 126, 124, 123, 164, 158, 67, 21, 139, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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