Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d07cbee440e06d4d2b7cdff2d3b630cbfca5ad28c660874f7b4ae31e132e8f

Tx prefix hash: 2d35f1b2f768f4a3a42123528ac5be4e8894fb1e2578b8440745b24f7d8cbd59
Tx public key: 5bb0fe88e88756938bb856f0faf3339a8839bbd7b88ac85443aa31d5e1daf700
Timestamp: 1767898208 Timestamp [UCT]: 2026-01-08 18:50:08 Age [y:d:h:m:s]: 00:014:03:24:36
Block: 1451518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9984 RingCT/type: yes/0
Extra: 015bb0fe88e88756938bb856f0faf3339a8839bbd7b88ac85443aa31d5e1daf700021100000010215bbf89000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4266dc46e8c2e87c47ce5c68716da019136deec554cc1c4e808252d107bb52e0 0.600000000000 1940530 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": 1451528, "vin": [ { "gen": { "height": 1451518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4266dc46e8c2e87c47ce5c68716da019136deec554cc1c4e808252d107bb52e0" } } ], "extra": [ 1, 91, 176, 254, 136, 232, 135, 86, 147, 139, 184, 86, 240, 250, 243, 51, 154, 136, 57, 187, 215, 184, 138, 200, 84, 67, 170, 49, 213, 225, 218, 247, 0, 2, 17, 0, 0, 0, 16, 33, 91, 191, 137, 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