Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5eb9eda847b602fb078fc28250703cb2b8ebe9cab09fe4a292fb7748283cbfb

Tx prefix hash: b01a9104eab26d32684f35c2d790515220c14a1dc6369cdb317fd2a75bf7c7af
Tx public key: 424108c37a5f297edd029503d6f8c74075b0b20edd0a08ab54e504e17c045679
Timestamp: 1737183634 Timestamp [UCT]: 2025-01-18 07:00:34 Age [y:d:h:m:s]: 00:150:19:30:39
Block: 1199873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107483 RingCT/type: yes/0
Extra: 01424108c37a5f297edd029503d6f8c74075b0b20edd0a08ab54e504e17c0456790211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5b87c60ed178a97a71a10b7bec3d5a0b643f5e9b416ebdf30833cc452c4f1b7 0.600000000000 1686508 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": 1199883, "vin": [ { "gen": { "height": 1199873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5b87c60ed178a97a71a10b7bec3d5a0b643f5e9b416ebdf30833cc452c4f1b7" } } ], "extra": [ 1, 66, 65, 8, 195, 122, 95, 41, 126, 221, 2, 149, 3, 214, 248, 199, 64, 117, 176, 178, 14, 221, 10, 8, 171, 84, 229, 4, 225, 124, 4, 86, 121, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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