Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7eba29a55b8e283c3f053e434ea314f0ecb7774eda11495e2c384152ef8009b

Tx prefix hash: 359eed456c4b24f2cac4f325633e801772cadfc69ca3f98112229f43c3c25c72
Tx public key: 50a6067e16d06972cee552237ea90a60d78cbaaf345db59d6acaf1fb2ac261a1
Timestamp: 1719249524 Timestamp [UCT]: 2024-06-24 17:18:44 Age [y:d:h:m:s]: 00:359:07:18:59
Block: 1051317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256691 RingCT/type: yes/0
Extra: 0150a6067e16d06972cee552237ea90a60d78cbaaf345db59d6acaf1fb2ac261a1021100000001a6fba9af000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e48f451a15df18113c03c3f3d48bf2426d8a3efa7e7ad50abf6fadaca00b6c1 0.600000000000 1521626 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": 1051327, "vin": [ { "gen": { "height": 1051317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e48f451a15df18113c03c3f3d48bf2426d8a3efa7e7ad50abf6fadaca00b6c1" } } ], "extra": [ 1, 80, 166, 6, 126, 22, 208, 105, 114, 206, 229, 82, 35, 126, 169, 10, 96, 215, 140, 186, 175, 52, 93, 181, 157, 106, 202, 241, 251, 42, 194, 97, 161, 2, 17, 0, 0, 0, 1, 166, 251, 169, 175, 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