Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56e94465e7a3aa17686eaeeee4fcfef754e5a08cb0e3bc3cbefe32ca3845b13c

Tx prefix hash: d977b78e57b01d91bf51e355ad88cba8948c54d0fd729b588f9d95e0f7fa101c
Tx public key: 164a034b7d151ad33e995374c973ad8e5d890d2a91652e5b4e32e6346ed455f2
Timestamp: 1756615268 Timestamp [UCT]: 2025-08-31 04:41:08 Age [y:d:h:m:s]: 00:121:07:24:54
Block: 1358156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86704 RingCT/type: yes/0
Extra: 01164a034b7d151ad33e995374c973ad8e5d890d2a91652e5b4e32e6346ed455f2021100000005a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbaa8f22a1d00ff2ffac1de3c1793fe37fc3e8c18f85c52fe8e1bd401dcb9bb1 0.600000000000 1846167 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": 1358166, "vin": [ { "gen": { "height": 1358156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbaa8f22a1d00ff2ffac1de3c1793fe37fc3e8c18f85c52fe8e1bd401dcb9bb1" } } ], "extra": [ 1, 22, 74, 3, 75, 125, 21, 26, 211, 62, 153, 83, 116, 201, 115, 173, 142, 93, 137, 13, 42, 145, 101, 46, 91, 78, 50, 230, 52, 110, 212, 85, 242, 2, 17, 0, 0, 0, 5, 161, 29, 186, 152, 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