Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e25aecb4afd9987b772f64de1890ff04a01fe95314e038b337a5cca63717b83e

Tx prefix hash: 662d691d54cde21806ea6e57f1e1fd53b2198af21ce4ddb04643cb8d57be1be5
Tx public key: 2479787b90863b26c4ea0f35ce3adbc8028d18bf3dde0ac4c8b49d1738b1596f
Timestamp: 1659336508 Timestamp [UCT]: 2022-08-01 06:48:28 Age [y:d:h:m:s]: 02:153:21:20:34
Block: 556218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 631403 RingCT/type: yes/0
Extra: 012479787b90863b26c4ea0f35ce3adbc8028d18bf3dde0ac4c8b49d1738b1596f021100000011eae24e24000000000000000000

1 output(s) for total of 8.810874029000 dcy

stealth address amount amount idx
00: b427a926e6391a6135c144809e9984679239225620e5c03116db5fbef138067c 8.810874029000 988144 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": 556228, "vin": [ { "gen": { "height": 556218 } } ], "vout": [ { "amount": 8810874029, "target": { "key": "b427a926e6391a6135c144809e9984679239225620e5c03116db5fbef138067c" } } ], "extra": [ 1, 36, 121, 120, 123, 144, 134, 59, 38, 196, 234, 15, 53, 206, 58, 219, 200, 2, 141, 24, 191, 61, 222, 10, 196, 200, 180, 157, 23, 56, 177, 89, 111, 2, 17, 0, 0, 0, 17, 234, 226, 78, 36, 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