Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29b3a79440f0c664085226c8058cf520b7edd1cb9abf803a98bdd061932067f5

Tx prefix hash: be7000a82b294d9cf11e25bd43e2a80b20492a1440b7cdca748373dfda64352b
Tx public key: cc719ce0a150083fd078f0add7f2e937fe45a934244ad1e398e5cbd531d0e2df
Timestamp: 1764224422 Timestamp [UCT]: 2025-11-27 06:20:22 Age [y:d:h:m:s]: 00:008:10:33:25
Block: 1421066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6034 RingCT/type: yes/0
Extra: 01cc719ce0a150083fd078f0add7f2e937fe45a934244ad1e398e5cbd531d0e2df0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f30106eece88ef1cdd5c2921bc65e27b4e21e9ed503ec7037007757a8f60728 0.600000000000 1909621 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": 1421076, "vin": [ { "gen": { "height": 1421066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f30106eece88ef1cdd5c2921bc65e27b4e21e9ed503ec7037007757a8f60728" } } ], "extra": [ 1, 204, 113, 156, 224, 161, 80, 8, 63, 208, 120, 240, 173, 215, 242, 233, 55, 254, 69, 169, 52, 36, 74, 209, 227, 152, 229, 203, 213, 49, 208, 226, 223, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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