Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c3c4730f392d352a62501289167d25233fc6041f7a8d18556904e8a0f0e770

Tx prefix hash: 9f6e1362fc1c5cec9c8a54f299ce9b77d118ed6918e2715bf423f81d02d0ce71
Tx public key: 4076690094efe8d69be5b4f277c29c21a78c038924ed88e3a33ac2694b16da88
Timestamp: 1751783699 Timestamp [UCT]: 2025-07-06 06:34:59 Age [y:d:h:m:s]: 00:132:19:53:11
Block: 1319761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93318 RingCT/type: yes/0
Extra: 014076690094efe8d69be5b4f277c29c21a78c038924ed88e3a33ac2694b16da88021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d58160ffd0755dfaed772ffd2c60219ff87e97d792c7c2f4f7b764528201f4f3 0.600000000000 1807454 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": 1319771, "vin": [ { "gen": { "height": 1319761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d58160ffd0755dfaed772ffd2c60219ff87e97d792c7c2f4f7b764528201f4f3" } } ], "extra": [ 1, 64, 118, 105, 0, 148, 239, 232, 214, 155, 229, 180, 242, 119, 194, 156, 33, 167, 140, 3, 137, 36, 237, 136, 227, 163, 58, 194, 105, 75, 22, 218, 136, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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