Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62336d54b0852f75009a560c8b57c6ca484b440d0ca21a3143ed171ad7fe7f7f

Tx prefix hash: a146935d8a36805eee814635347df28a612ff4edf8ff873f9d46f2630c20132f
Tx public key: 0c291f437e837e3d5ca31a9b11a76869d996bc70d09aca1701a2fb727d7b0479
Timestamp: 1729285033 Timestamp [UCT]: 2024-10-18 20:57:13 Age [y:d:h:m:s]: 00:200:01:59:49
Block: 1134528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142799 RingCT/type: yes/0
Extra: 010c291f437e837e3d5ca31a9b11a76869d996bc70d09aca1701a2fb727d7b04790211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b11a87aee070d60a14e416a86b1e3adf9be5ce0490c2db2c2a02ad02c94bcea 0.600000000000 1617843 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": 1134538, "vin": [ { "gen": { "height": 1134528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b11a87aee070d60a14e416a86b1e3adf9be5ce0490c2db2c2a02ad02c94bcea" } } ], "extra": [ 1, 12, 41, 31, 67, 126, 131, 126, 61, 92, 163, 26, 155, 17, 167, 104, 105, 217, 150, 188, 112, 208, 154, 202, 23, 1, 162, 251, 114, 125, 123, 4, 121, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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