Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ceaf0297dfc36763fb17975abb2a7026aed3aa945c562d5a4e4001a92019420

Tx prefix hash: ef78b4280ba684f4f41baf8766a3c66e4bb601dcd06d504de48e6285ee36b6d9
Tx public key: 723a8343ee08781c6ef2c6783ccaa5670d99f13884e2345c15d7f9e5ba14fe00
Timestamp: 1698240095 Timestamp [UCT]: 2023-10-25 13:21:35 Age [y:d:h:m:s]: 01:160:03:09:02
Block: 877372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375439 RingCT/type: yes/0
Extra: 01723a8343ee08781c6ef2c6783ccaa5670d99f13884e2345c15d7f9e5ba14fe000211000000044b8f5122000000000000000000

1 output(s) for total of 0.760155367000 dcy

stealth address amount amount idx
00: 86e2906c19d61a6e1321ca45cd9b7d85c40b1fd073c57cee14a4988d455b7694 0.760155367000 1332746 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": 877382, "vin": [ { "gen": { "height": 877372 } } ], "vout": [ { "amount": 760155367, "target": { "key": "86e2906c19d61a6e1321ca45cd9b7d85c40b1fd073c57cee14a4988d455b7694" } } ], "extra": [ 1, 114, 58, 131, 67, 238, 8, 120, 28, 110, 242, 198, 120, 60, 202, 165, 103, 13, 153, 241, 56, 132, 226, 52, 92, 21, 215, 249, 229, 186, 20, 254, 0, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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