Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93fd06eeeae377177303b8935d97fcd60561f6a031e6c1175a53947e47fa43fb

Tx prefix hash: a3136426bddb7af03809cb24ec2218f6cdbbe305a6ee910de39f1ab89316eb99
Tx public key: df8d23ca5095cc38ccde77e2a51059322acd2e7467a34f5e7de867ec0a3d632f
Timestamp: 1719441252 Timestamp [UCT]: 2024-06-26 22:34:12 Age [y:d:h:m:s]: 00:263:13:56:12
Block: 1052916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188353 RingCT/type: yes/0
Extra: 01df8d23ca5095cc38ccde77e2a51059322acd2e7467a34f5e7de867ec0a3d632f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a3ad20539e63aa1e66b9a908e1f85a5f34ecd45c97c7595d3d19678bcc9b8d6 0.600000000000 1523261 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": 1052926, "vin": [ { "gen": { "height": 1052916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a3ad20539e63aa1e66b9a908e1f85a5f34ecd45c97c7595d3d19678bcc9b8d6" } } ], "extra": [ 1, 223, 141, 35, 202, 80, 149, 204, 56, 204, 222, 119, 226, 165, 16, 89, 50, 42, 205, 46, 116, 103, 163, 79, 94, 125, 232, 103, 236, 10, 61, 99, 47, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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