Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68daea56da9766a2c2e309c153e146ff789e1dd03eae46ef6e93222b6cf43f64

Tx prefix hash: 3c0ef1bd04731043dc0a8e8a31a1cdff3d863dd1b27412bea3dcdb2c2c00d8f0
Tx public key: edf3549d3e30cbb1e8b142e2f4bba14ca7910972d5b2fd4912d84221eebb3c33
Timestamp: 1763484635 Timestamp [UCT]: 2025-11-18 16:50:35 Age [y:d:h:m:s]: 00:009:13:02:20
Block: 1414939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6833 RingCT/type: yes/0
Extra: 01edf3549d3e30cbb1e8b142e2f4bba14ca7910972d5b2fd4912d84221eebb3c330211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0faa4d60ec88548b09360faa73a874e52d9468660cd615dcf43dd1a98d3d10d9 0.600000000000 1903432 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": 1414949, "vin": [ { "gen": { "height": 1414939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0faa4d60ec88548b09360faa73a874e52d9468660cd615dcf43dd1a98d3d10d9" } } ], "extra": [ 1, 237, 243, 84, 157, 62, 48, 203, 177, 232, 177, 66, 226, 244, 187, 161, 76, 167, 145, 9, 114, 213, 178, 253, 73, 18, 216, 66, 33, 238, 187, 60, 51, 2, 17, 0, 0, 0, 1, 140, 235, 127, 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