Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc35ad5d1bf91fc1dbfcf95978ed7c15441594d11a32d4ce18d8051e3e9dfa47

Tx prefix hash: ffea1e8a429fb033fc81cb0f916a2f6770478cf9ccdf79e3aa4af2bba01bf334
Tx public key: 3cc219868406e4845b43fb6f0c2289117e7d14407334e92f60bed4fb414671ae
Timestamp: 1761386385 Timestamp [UCT]: 2025-10-25 09:59:45 Age [y:d:h:m:s]: 00:098:05:55:40
Block: 1397560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70162 RingCT/type: yes/0
Extra: 013cc219868406e4845b43fb6f0c2289117e7d14407334e92f60bed4fb414671ae0211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21f4888550a0d0b4dd0c193c4a0daf0f8b3eeed5c739ce27449086061f7c67d5 0.600000000000 1885851 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": 1397570, "vin": [ { "gen": { "height": 1397560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21f4888550a0d0b4dd0c193c4a0daf0f8b3eeed5c739ce27449086061f7c67d5" } } ], "extra": [ 1, 60, 194, 25, 134, 132, 6, 228, 132, 91, 67, 251, 111, 12, 34, 137, 17, 126, 125, 20, 64, 115, 52, 233, 47, 96, 190, 212, 251, 65, 70, 113, 174, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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