Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26bda38ac4fb32ad9fb16809cf9c413721b33adb2a8da1537aa437f24b7c5c91

Tx prefix hash: bbe3261ee630ae147add50c4f239703ea90a541d16c9289832e7658c4b4e96b6
Tx public key: 168d292e8b56e4375a122974734db50bdff181711604c08f0e0c9f5cae3c092a
Timestamp: 1761741162 Timestamp [UCT]: 2025-10-29 12:32:42 Age [y:d:h:m:s]: 00:011:07:08:11
Block: 1400504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8079 RingCT/type: yes/0
Extra: 01168d292e8b56e4375a122974734db50bdff181711604c08f0e0c9f5cae3c092a021100000006df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eec4daba9999d3ea110e123ec9de68e89586f5464a56e8feaed3f941f771fd6 0.600000000000 1888813 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": 1400514, "vin": [ { "gen": { "height": 1400504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eec4daba9999d3ea110e123ec9de68e89586f5464a56e8feaed3f941f771fd6" } } ], "extra": [ 1, 22, 141, 41, 46, 139, 86, 228, 55, 90, 18, 41, 116, 115, 77, 181, 11, 223, 241, 129, 113, 22, 4, 192, 143, 14, 12, 159, 92, 174, 60, 9, 42, 2, 17, 0, 0, 0, 6, 223, 90, 36, 122, 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