Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0109cd7e580c46bc7da6df814f0b4c2c5d26afbf70d97c651dcbfce03c1ecb

Tx prefix hash: fc0922b1eb7e4a3e73573a1ee34d85631bbc21d9cbf2d31b2268382242a87267
Tx public key: e09b8fd195d60e8d66f59e5293c39d51fce10c7c4cb0eff58483da5cc6c892d6
Timestamp: 1762024692 Timestamp [UCT]: 2025-11-01 19:18:12 Age [y:d:h:m:s]: 00:055:22:21:58
Block: 1402847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40038 RingCT/type: yes/0
Extra: 01e09b8fd195d60e8d66f59e5293c39d51fce10c7c4cb0eff58483da5cc6c892d602110000000625a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71fd8a36e0b9dd5ab5575afa5d661769dcc52a9b4d5ca91f2582bc08fae95b92 0.600000000000 1891172 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": 1402857, "vin": [ { "gen": { "height": 1402847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71fd8a36e0b9dd5ab5575afa5d661769dcc52a9b4d5ca91f2582bc08fae95b92" } } ], "extra": [ 1, 224, 155, 143, 209, 149, 214, 14, 141, 102, 245, 158, 82, 147, 195, 157, 81, 252, 225, 12, 124, 76, 176, 239, 245, 132, 131, 218, 92, 198, 200, 146, 214, 2, 17, 0, 0, 0, 6, 37, 163, 90, 15, 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