Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33d6f8507cb73b5ec9dd782f394f24812443a4e9adcf2995473b271f938abf26

Tx prefix hash: 525c7b9361266d1dadc7e3bfbb79350c057c05e07a4fbb0cb7119a7e7bf57e22
Tx public key: 371d6b826c14c268e9ba2388654075ce8f06666a401f21dab59e6c01bd31fc63
Timestamp: 1761891307 Timestamp [UCT]: 2025-10-31 06:15:07 Age [y:d:h:m:s]: 00:009:21:57:06
Block: 1401744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7091 RingCT/type: yes/0
Extra: 01371d6b826c14c268e9ba2388654075ce8f06666a401f21dab59e6c01bd31fc63021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4d79fe7f952cc98e182e1cbc3dcb66c148e7f814cba0f04ded50040d0feb731 0.600000000000 1890063 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": 1401754, "vin": [ { "gen": { "height": 1401744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4d79fe7f952cc98e182e1cbc3dcb66c148e7f814cba0f04ded50040d0feb731" } } ], "extra": [ 1, 55, 29, 107, 130, 108, 20, 194, 104, 233, 186, 35, 136, 101, 64, 117, 206, 143, 6, 102, 106, 64, 31, 33, 218, 181, 158, 108, 1, 189, 49, 252, 99, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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