Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d5f9363b92ab2c62f860e993b35676a2ed06c7f493df6300cfd0e73ffca535

Tx prefix hash: 1b60b40173f1c564399ef267cf3a47b68850a52255989180197a37ddb6276c39
Tx public key: d58772e25af8413dd8f0e0aa9096acc0a75caf1d7c1782c730b5583b4931fafc
Timestamp: 1764167819 Timestamp [UCT]: 2025-11-26 14:36:59 Age [y:d:h:m:s]: 00:001:04:17:35
Block: 1420596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 858 RingCT/type: yes/0
Extra: 01d58772e25af8413dd8f0e0aa9096acc0a75caf1d7c1782c730b5583b4931fafc02110000000bd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f2297df0d6b05f7cfc67c154e2972df8d23cac9de64d75625279ad3ed7bc47b 0.600000000000 1909145 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": 1420606, "vin": [ { "gen": { "height": 1420596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f2297df0d6b05f7cfc67c154e2972df8d23cac9de64d75625279ad3ed7bc47b" } } ], "extra": [ 1, 213, 135, 114, 226, 90, 248, 65, 61, 216, 240, 224, 170, 144, 150, 172, 192, 167, 92, 175, 29, 124, 23, 130, 199, 48, 181, 88, 59, 73, 49, 250, 252, 2, 17, 0, 0, 0, 11, 214, 225, 157, 124, 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