Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: becfbfdfdfb77d5921a4788cd8796e10a407a93d6dc2739537b5965fd2c77f98

Tx prefix hash: b9abad73736e89a14a71d5604c161b59492a31f39c51a9ef21b941a6bcbbc2c7
Tx public key: 7a147f3d9386a46df697bd23d3e0af0a96b0109e37b3469786a81f3617f547ff
Timestamp: 1702082644 Timestamp [UCT]: 2023-12-09 00:44:04 Age [y:d:h:m:s]: 01:130:18:33:55
Block: 909002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354613 RingCT/type: yes/0
Extra: 017a147f3d9386a46df697bd23d3e0af0a96b0109e37b3469786a81f3617f547ff02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a659dc75866d4be68c6f8010923e2f4a4db5b21b59bdd994b1b143a98e46ade 0.600000000000 1366067 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": 909012, "vin": [ { "gen": { "height": 909002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a659dc75866d4be68c6f8010923e2f4a4db5b21b59bdd994b1b143a98e46ade" } } ], "extra": [ 1, 122, 20, 127, 61, 147, 134, 164, 109, 246, 151, 189, 35, 211, 224, 175, 10, 150, 176, 16, 158, 55, 179, 70, 151, 134, 168, 31, 54, 23, 245, 71, 255, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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