Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9116c38e0e250ee5a4a03d5226bf544256bfbf7a33f41fd52f24995e03c33381

Tx prefix hash: ebc6d76780abd13560ba26424d1e98d467204c965aaf5e2bb32d1b7c92dec2c6
Tx public key: b4be2ea91d56e5a09a258f43546dfee679a5d1e604d28b14a8627889b6c5627d
Timestamp: 1728969458 Timestamp [UCT]: 2024-10-15 05:17:38 Age [y:d:h:m:s]: 00:100:17:05:29
Block: 1131919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71940 RingCT/type: yes/0
Extra: 01b4be2ea91d56e5a09a258f43546dfee679a5d1e604d28b14a8627889b6c5627d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49aaba625044f097b3e621284e288611a591d4a8561e21e2c3c59461d7ace905 0.600000000000 1614828 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": 1131929, "vin": [ { "gen": { "height": 1131919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49aaba625044f097b3e621284e288611a591d4a8561e21e2c3c59461d7ace905" } } ], "extra": [ 1, 180, 190, 46, 169, 29, 86, 229, 160, 154, 37, 143, 67, 84, 109, 254, 230, 121, 165, 209, 230, 4, 210, 139, 20, 168, 98, 120, 137, 182, 197, 98, 125, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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