Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16664e2bd7cd904af098eda83d4e1a7da49ed9e7460551a11261449345bed1b

Tx prefix hash: 6e1d6c58e342f128a05af6ea955d2d1c6a90366d8c492cde27d0c2d0571a00d0
Tx public key: 7cca3d6970c95ba238f3f5054cda63845d2f04721d4c31cfcfb2e07391d198a6
Timestamp: 1753886525 Timestamp [UCT]: 2025-07-30 14:42:05 Age [y:d:h:m:s]: 00:020:05:13:33
Block: 1336707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13379 RingCT/type: yes/0
Extra: 017cca3d6970c95ba238f3f5054cda63845d2f04721d4c31cfcfb2e07391d198a6021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 714330e9e2febc211f118a2ef5533525622fbe60fa561c1e2fc600d79585b943 0.600000000000 1824508 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": 1336717, "vin": [ { "gen": { "height": 1336707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "714330e9e2febc211f118a2ef5533525622fbe60fa561c1e2fc600d79585b943" } } ], "extra": [ 1, 124, 202, 61, 105, 112, 201, 91, 162, 56, 243, 245, 5, 76, 218, 99, 132, 93, 47, 4, 114, 29, 76, 49, 207, 207, 178, 224, 115, 145, 209, 152, 166, 2, 17, 0, 0, 0, 4, 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