Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3db5db47c6f059be68140573177c536e2564f64cf2265202f10d7c9f8b53347d

Tx prefix hash: f27e8361e49ecee9d0fc5a9f656480a39aa0b620ded2d1154d08d41946e1d0d4
Tx public key: 6cee5366d6b629a8f7e61ac3e4408fa4fb88d9a6922793364584ff9413bbe4af
Timestamp: 1763404592 Timestamp [UCT]: 2025-11-17 18:36:32 Age [y:d:h:m:s]: 00:010:15:29:30
Block: 1414274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7623 RingCT/type: yes/0
Extra: 016cee5366d6b629a8f7e61ac3e4408fa4fb88d9a6922793364584ff9413bbe4af0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4185a430e677a1c1f4191d3b979fe5a7b1078c040727d4c75abeb1e42eeec191 0.600000000000 1902761 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": 1414284, "vin": [ { "gen": { "height": 1414274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4185a430e677a1c1f4191d3b979fe5a7b1078c040727d4c75abeb1e42eeec191" } } ], "extra": [ 1, 108, 238, 83, 102, 214, 182, 41, 168, 247, 230, 26, 195, 228, 64, 143, 164, 251, 136, 217, 166, 146, 39, 147, 54, 69, 132, 255, 148, 19, 187, 228, 175, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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