Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42816de4dd2d365b9b7c3f0769a354dad11159abc7597b4863435114bda01b9a

Tx prefix hash: 4d4f12ecb409795058c04881a0adc48f5a7d8faecaf161f0cc0d96d4517ac7e5
Tx public key: efff675423f4e7f1b71d788b7c74a4f5cfac8a67f561205b4ebbbd3443108ed2
Timestamp: 1753933624 Timestamp [UCT]: 2025-07-31 03:47:04 Age [y:d:h:m:s]: 00:118:10:31:26
Block: 1337083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83505 RingCT/type: yes/0
Extra: 01efff675423f4e7f1b71d788b7c74a4f5cfac8a67f561205b4ebbbd3443108ed2021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84344c67507619d2e1ad33f4d062eb8c3c56982f39e5da0af33b6f81bcbfa60a 0.600000000000 1824886 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": 1337093, "vin": [ { "gen": { "height": 1337083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84344c67507619d2e1ad33f4d062eb8c3c56982f39e5da0af33b6f81bcbfa60a" } } ], "extra": [ 1, 239, 255, 103, 84, 35, 244, 231, 241, 183, 29, 120, 139, 124, 116, 164, 245, 207, 172, 138, 103, 245, 97, 32, 91, 78, 187, 189, 52, 67, 16, 142, 210, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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