Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae3b5b3c93f22d4e0fb5d40c0aab506d65d9970ea7edd72a1094ffcacf42b08

Tx prefix hash: 9b04b3898957739cbbc7ac646c311f01ccf0762ba406867916e3a4422810c7e2
Tx public key: eac098937881d172e81ea0ffb1546b0a2f80b7f832d460efa1aef769f9b34bba
Timestamp: 1735454293 Timestamp [UCT]: 2024-12-29 06:38:13 Age [y:d:h:m:s]: 00:096:07:09:43
Block: 1185541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68618 RingCT/type: yes/0
Extra: 01eac098937881d172e81ea0ffb1546b0a2f80b7f832d460efa1aef769f9b34bba0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 520222123d717ee3ea1754e4b92a2f393baa110fcd6833d189de4bae334f653b 0.600000000000 1672014 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": 1185551, "vin": [ { "gen": { "height": 1185541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "520222123d717ee3ea1754e4b92a2f393baa110fcd6833d189de4bae334f653b" } } ], "extra": [ 1, 234, 192, 152, 147, 120, 129, 209, 114, 232, 30, 160, 255, 177, 84, 107, 10, 47, 128, 183, 248, 50, 212, 96, 239, 161, 174, 247, 105, 249, 179, 75, 186, 2, 17, 0, 0, 0, 4, 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