Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9652f8946607f40106a48d1c1a1cf6950e5e3d9229905cde7be16a9936619b78

Tx prefix hash: a366ed64b90b12a772c05b05c6efe89ee9ec094fa19471e231e7c83e73f7312f
Tx public key: 3b6dbe2e2c243574ae230c3b3307c599928127581aa084b7c2bc22b28ee49a05
Timestamp: 1743160360 Timestamp [UCT]: 2025-03-28 11:12:40 Age [y:d:h:m:s]: 00:236:19:57:35
Block: 1249079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166995 RingCT/type: yes/0
Extra: 013b6dbe2e2c243574ae230c3b3307c599928127581aa084b7c2bc22b28ee49a05021100000003d2e40efd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff2c7db0818cc8b24d94502955f35ab725e61154d37356850a872be194f7c06b 0.600000000000 1736114 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": 1249089, "vin": [ { "gen": { "height": 1249079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff2c7db0818cc8b24d94502955f35ab725e61154d37356850a872be194f7c06b" } } ], "extra": [ 1, 59, 109, 190, 46, 44, 36, 53, 116, 174, 35, 12, 59, 51, 7, 197, 153, 146, 129, 39, 88, 26, 160, 132, 183, 194, 188, 34, 178, 142, 228, 154, 5, 2, 17, 0, 0, 0, 3, 210, 228, 14, 253, 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