Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8ce1f57f40cbaf3c36fa192527eeacb572dde5741f10a9f7134a3efee76130

Tx prefix hash: 5da625c3621826c22ac8bf64a247ca25f5682804c06b44ff90be29ae6a45013c
Tx public key: 8c3849c34b3c31e3d30179f8e141e62f313257843a01bcfab0e22b3154d295a4
Timestamp: 1719782037 Timestamp [UCT]: 2024-06-30 21:13:57 Age [y:d:h:m:s]: 00:257:03:45:59
Block: 1055737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183763 RingCT/type: yes/0
Extra: 018c3849c34b3c31e3d30179f8e141e62f313257843a01bcfab0e22b3154d295a4021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5246ea00c02ab80313d0c2c68713147aac8f5ec60a8938619c9b6ff03efe0d7 0.600000000000 1526142 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": 1055747, "vin": [ { "gen": { "height": 1055737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5246ea00c02ab80313d0c2c68713147aac8f5ec60a8938619c9b6ff03efe0d7" } } ], "extra": [ 1, 140, 56, 73, 195, 75, 60, 49, 227, 211, 1, 121, 248, 225, 65, 230, 47, 49, 50, 87, 132, 58, 1, 188, 250, 176, 226, 43, 49, 84, 210, 149, 164, 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