Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7631735ed61e6d347b4e4b68a35f8fd8f14e2fe5379534f1e1d8a4e227546586

Tx prefix hash: 49e5fe6e1d6d47d628514eb2c19d9bfe4d90e6cd18bbba75d80995a67ed3975e
Tx public key: bef636bcc70aa232f8c458f5c2417dfe6f8c70cad7a1dffcd5dfab77b0d24720
Timestamp: 1719788802 Timestamp [UCT]: 2024-06-30 23:06:42 Age [y:d:h:m:s]: 01:130:07:51:08
Block: 1055799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351682 RingCT/type: yes/0
Extra: 01bef636bcc70aa232f8c458f5c2417dfe6f8c70cad7a1dffcd5dfab77b0d24720021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 840dfa1e7c0d7ef10fd2d1277053ea037086e4279f7515372cba2f0b12a7a8da 0.600000000000 1526204 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": 1055809, "vin": [ { "gen": { "height": 1055799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "840dfa1e7c0d7ef10fd2d1277053ea037086e4279f7515372cba2f0b12a7a8da" } } ], "extra": [ 1, 190, 246, 54, 188, 199, 10, 162, 50, 248, 196, 88, 245, 194, 65, 125, 254, 111, 140, 112, 202, 215, 161, 223, 252, 213, 223, 171, 119, 176, 210, 71, 32, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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