Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3b2931c52d79c3c1cc9c74f87e55dd5902bc7b9f809d944ee9398f8c7311f72

Tx prefix hash: f92c3d5d9c34982dde40b7bdbc893d3c8f49021eb3f007f9bfabdebf960a6acd
Tx public key: 49cfc859e2950e311cd68f61edb7e75d0eb516c7045c60bab3f88c61959bce0b
Timestamp: 1763405222 Timestamp [UCT]: 2025-11-17 18:47:02 Age [y:d:h:m:s]: 00:051:17:56:43
Block: 1414279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37060 RingCT/type: yes/0
Extra: 0149cfc859e2950e311cd68f61edb7e75d0eb516c7045c60bab3f88c61959bce0b021100000002da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64aa741ad0c47c9cb39fba706c6cb8d817aa980dd11a9f03d89157551e27c692 0.600000000000 1902766 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": 1414289, "vin": [ { "gen": { "height": 1414279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64aa741ad0c47c9cb39fba706c6cb8d817aa980dd11a9f03d89157551e27c692" } } ], "extra": [ 1, 73, 207, 200, 89, 226, 149, 14, 49, 28, 214, 143, 97, 237, 183, 231, 93, 14, 181, 22, 199, 4, 92, 96, 186, 179, 248, 140, 97, 149, 155, 206, 11, 2, 17, 0, 0, 0, 2, 218, 85, 72, 72, 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