Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f9e442448827a63d5c5a03ce3a9740fd4818f182e0a5158074923e897f8a9ef

Tx prefix hash: 0f05a843d5535fb0578bd2acd3a982e192e48d0386ce8aeb5cce5da40ddb73d4
Tx public key: 6b5e8a54ef305bcaa63c44adad3845ef5bdafebbac96e59fa93a2a615dc5f323
Timestamp: 1729819149 Timestamp [UCT]: 2024-10-25 01:19:09 Age [y:d:h:m:s]: 00:191:18:03:17
Block: 1138923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136860 RingCT/type: yes/0
Extra: 016b5e8a54ef305bcaa63c44adad3845ef5bdafebbac96e59fa93a2a615dc5f3230211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cd45cf1aa1147670ad94816e1ea6e4f38f1b332e6e7f6d7f4ed5797196a28f3 0.600000000000 1622664 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": 1138933, "vin": [ { "gen": { "height": 1138923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cd45cf1aa1147670ad94816e1ea6e4f38f1b332e6e7f6d7f4ed5797196a28f3" } } ], "extra": [ 1, 107, 94, 138, 84, 239, 48, 91, 202, 166, 60, 68, 173, 173, 56, 69, 239, 91, 218, 254, 187, 172, 150, 229, 159, 169, 58, 42, 97, 93, 197, 243, 35, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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