Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcca9774c3be6ad0c2411422e5650810c6f95a24c94693fc0103eeba614ccae1

Tx prefix hash: 749d4e671434b0e5cc2f1f54836eb65a2c1cfa84d908a74b94ae566dd99812dd
Tx public key: 39db86b822207d011db563a6025abf96a8308ccb7c0907770adfc4d2b7e262cb
Timestamp: 1764888704 Timestamp [UCT]: 2025-12-04 22:51:44 Age [y:d:h:m:s]: 00:030:11:27:12
Block: 1426587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21823 RingCT/type: yes/0
Extra: 0139db86b822207d011db563a6025abf96a8308ccb7c0907770adfc4d2b7e262cb021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3be6fb057333d6d069dcffb48a0b37ef1e3b49eb77fa0c15f80365e95c428c0 0.600000000000 1915280 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": 1426597, "vin": [ { "gen": { "height": 1426587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3be6fb057333d6d069dcffb48a0b37ef1e3b49eb77fa0c15f80365e95c428c0" } } ], "extra": [ 1, 57, 219, 134, 184, 34, 32, 125, 1, 29, 181, 99, 166, 2, 90, 191, 150, 168, 48, 140, 203, 124, 9, 7, 119, 10, 223, 196, 210, 183, 226, 98, 203, 2, 17, 0, 0, 0, 4, 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