Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ccbb7f7561952168631ddf981b72a4e499b615cec58e14dc6dd7330d18fcb89

Tx prefix hash: 3a4fcc5c0de5a223d7e1adc27ec6d38b572e4158c5c9145905a56339c777cd06
Tx public key: 9a7b8a035a39bd4950fe6b9bb7f532858e68601ba7d773cc34f6fd86ed421a8b
Timestamp: 1755696509 Timestamp [UCT]: 2025-08-20 13:28:29 Age [y:d:h:m:s]: 00:091:18:33:00
Block: 1350604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65501 RingCT/type: yes/0
Extra: 019a7b8a035a39bd4950fe6b9bb7f532858e68601ba7d773cc34f6fd86ed421a8b0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64ab73107a5d0413f5f0c9023527f1d2e6497902ec8a8e3eafc230d46417e99 0.600000000000 1838549 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": 1350614, "vin": [ { "gen": { "height": 1350604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64ab73107a5d0413f5f0c9023527f1d2e6497902ec8a8e3eafc230d46417e99" } } ], "extra": [ 1, 154, 123, 138, 3, 90, 57, 189, 73, 80, 254, 107, 155, 183, 245, 50, 133, 142, 104, 96, 27, 167, 215, 115, 204, 52, 246, 253, 134, 237, 66, 26, 139, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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