Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a1017b41a73a95ab87343c918402638cb64ea16dac9a677d341c363af78f60

Tx prefix hash: 00e29752e3d5c203e4a86d792c1ec2e92968368c1ddb85388105aaad65e28940
Tx public key: eb7f525b2cde2863359780a7311c82e5b77961362c9aac1e47fb2a1284e24a69
Timestamp: 1731591416 Timestamp [UCT]: 2024-11-14 13:36:56 Age [y:d:h:m:s]: 00:217:04:19:32
Block: 1153560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154962 RingCT/type: yes/0
Extra: 01eb7f525b2cde2863359780a7311c82e5b77961362c9aac1e47fb2a1284e24a69021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08dea73e408b4dd6055808f0742cef3b42c2e6c09a31c521902239a2243d4f27 0.600000000000 1639169 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": 1153570, "vin": [ { "gen": { "height": 1153560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08dea73e408b4dd6055808f0742cef3b42c2e6c09a31c521902239a2243d4f27" } } ], "extra": [ 1, 235, 127, 82, 91, 44, 222, 40, 99, 53, 151, 128, 167, 49, 28, 130, 229, 183, 121, 97, 54, 44, 154, 172, 30, 71, 251, 42, 18, 132, 226, 74, 105, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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