Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7998716fe9d832143de4fcba57ec5cc3282f9349f84e724120060e74b85c2f9d

Tx prefix hash: cf55bc3d7c688907c80bf9a171f0e6a4852689bbac8d477a4720b4f5c2df47b0
Tx public key: 2818a3b8249da10938cac4768d2214afd0bf80644fb0d9b838e359b1d5410dda
Timestamp: 1717581932 Timestamp [UCT]: 2024-06-05 10:05:32 Age [y:d:h:m:s]: 00:281:23:25:15
Block: 1037513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201521 RingCT/type: yes/0
Extra: 012818a3b8249da10938cac4768d2214afd0bf80644fb0d9b838e359b1d5410dda021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ef5bfb3e743435fd64bdcabdee4a0dedf1d4e0a113552d53f1a2fca0f3d04f8 0.600000000000 1506058 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": 1037523, "vin": [ { "gen": { "height": 1037513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ef5bfb3e743435fd64bdcabdee4a0dedf1d4e0a113552d53f1a2fca0f3d04f8" } } ], "extra": [ 1, 40, 24, 163, 184, 36, 157, 161, 9, 56, 202, 196, 118, 141, 34, 20, 175, 208, 191, 128, 100, 79, 176, 217, 184, 56, 227, 89, 177, 213, 65, 13, 218, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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