Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1cf67ede6317fc9509a975873a195dc49cf1624b30058df4227ff554914e7a

Tx prefix hash: 5f7eb34509508def0471dab656d731263713b887cfd73b973d0c80f4e1a18727
Tx public key: e5aae84d67f8cbf1511c5ce9d3c5e8516c96bf4ee4d94c863919818baca952b6
Timestamp: 1604482918 Timestamp [UCT]: 2020-11-04 09:41:58 Age [y:d:h:m:s]: 04:063:23:23:27
Block: 145895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1045465 RingCT/type: yes/0
Extra: 01e5aae84d67f8cbf1511c5ce9d3c5e8516c96bf4ee4d94c863919818baca952b602110000004e8b34f601000000000000000000

1 output(s) for total of 201.646179403000 dcy

stealth address amount amount idx
00: e10eebbb34b2d5f7e7c0005f83e26566cdcb90ebe25356a3c4e420faaaa275fe 201.646179403000 242427 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": 145905, "vin": [ { "gen": { "height": 145895 } } ], "vout": [ { "amount": 201646179403, "target": { "key": "e10eebbb34b2d5f7e7c0005f83e26566cdcb90ebe25356a3c4e420faaaa275fe" } } ], "extra": [ 1, 229, 170, 232, 77, 103, 248, 203, 241, 81, 28, 92, 233, 211, 197, 232, 81, 108, 150, 191, 78, 228, 217, 76, 134, 57, 25, 129, 139, 172, 169, 82, 182, 2, 17, 0, 0, 0, 78, 139, 52, 246, 1, 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