Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bacb95da130a55d5226b9bdf3a8d519195d6ffa7fc882e3e2898a2275005b210

Tx prefix hash: dc7276e84e718625f242d7359859cd6fc7c3e9cc34a30c1d52ba3020b4dfd3be
Tx public key: c1a22f344c74cff66bf163c68770d3e1e1d254479e3615443af9d540c8ea20bd
Timestamp: 1578919554 Timestamp [UCT]: 2020-01-13 12:45:54 Age [y:d:h:m:s]: 05:061:20:54:26
Block: 44617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194424 RingCT/type: yes/0
Extra: 01c1a22f344c74cff66bf163c68770d3e1e1d254479e3615443af9d540c8ea20bd0211000000c617786bcf000000000000000000

1 output(s) for total of 436.682912759000 dcy

stealth address amount amount idx
00: 25e2ad7d0f88d3e076d40997a96f4be923e81b0934db0afc7af2a6f124cce4cb 436.682912759000 81241 of 0

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": 44627, "vin": [ { "gen": { "height": 44617 } } ], "vout": [ { "amount": 436682912759, "target": { "key": "25e2ad7d0f88d3e076d40997a96f4be923e81b0934db0afc7af2a6f124cce4cb" } } ], "extra": [ 1, 193, 162, 47, 52, 76, 116, 207, 246, 107, 241, 99, 198, 135, 112, 211, 225, 225, 210, 84, 71, 158, 54, 21, 68, 58, 249, 213, 64, 200, 234, 32, 189, 2, 17, 0, 0, 0, 198, 23, 120, 107, 207, 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