Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66e9d6105300960b3da2b98966c48d1553f34b3bd8a00326540daca122879a73

Tx prefix hash: 171035090a81908b0eb761a8aeb0d1840d510c35ebfa6f81544a9747f1f464f3
Tx public key: 9dc7f0087a56fca719a800b81ae5c743aa1bcb290db1226a812e7da008588d72
Timestamp: 1759629960 Timestamp [UCT]: 2025-10-05 02:06:00 Age [y:d:h:m:s]: 00:038:07:09:13
Block: 1382986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27424 RingCT/type: yes/0
Extra: 019dc7f0087a56fca719a800b81ae5c743aa1bcb290db1226a812e7da008588d7202110000000697baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da3dfdebb54a0c175fd9c7c582106fa1d10c39fb20d034b7a9b9433bbd4a191c 0.600000000000 1871131 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": 1382996, "vin": [ { "gen": { "height": 1382986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da3dfdebb54a0c175fd9c7c582106fa1d10c39fb20d034b7a9b9433bbd4a191c" } } ], "extra": [ 1, 157, 199, 240, 8, 122, 86, 252, 167, 25, 168, 0, 184, 26, 229, 199, 67, 170, 27, 203, 41, 13, 177, 34, 106, 129, 46, 125, 160, 8, 88, 141, 114, 2, 17, 0, 0, 0, 6, 151, 186, 249, 34, 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