Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd68a46bf4b1e69c4a524c4849ca5c233d0792cf4817af03e854fc64b40fd3f8

Tx prefix hash: 00edab9adde84349b5640a7c4fc59f718f7c17554044db5ca26cafcd067faf8f
Tx public key: ed1b6b75318be03d7faf23d2e3136794bad37649751bc91ddc3f6fa6d44f3b04
Timestamp: 1747637532 Timestamp [UCT]: 2025-05-19 06:52:12 Age [y:d:h:m:s]: 00:141:22:11:32
Block: 1286146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99072 RingCT/type: yes/0
Extra: 01ed1b6b75318be03d7faf23d2e3136794bad37649751bc91ddc3f6fa6d44f3b040211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c10b4ec588cf1d17969d023dc6a3ac630da555e9bbbf6b7aed8f666159dae1 0.600000000000 1773611 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": 1286156, "vin": [ { "gen": { "height": 1286146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c10b4ec588cf1d17969d023dc6a3ac630da555e9bbbf6b7aed8f666159dae1" } } ], "extra": [ 1, 237, 27, 107, 117, 49, 139, 224, 61, 127, 175, 35, 210, 227, 19, 103, 148, 186, 211, 118, 73, 117, 27, 201, 29, 220, 63, 111, 166, 212, 79, 59, 4, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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