Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03204a03a06a08a231d122b6284b5f139acd4c2f611e3fddafcb85c516765f53

Tx prefix hash: 618a8207f402df3223c99173d67451f24adfed769e4067680ef9bfc7ce4f766d
Tx public key: 8d5b8999606f5535101ce820e11d4cf117494ae26d13481a253aa6a7087d3c74
Timestamp: 1674191015 Timestamp [UCT]: 2023-01-20 05:03:35 Age [y:d:h:m:s]: 02:078:01:04:23
Block: 678643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 577426 RingCT/type: yes/0
Extra: 018d5b8999606f5535101ce820e11d4cf117494ae26d13481a253aa6a7087d3c740211000000015029cbac000000000000000000

1 output(s) for total of 3.462373917000 dcy

stealth address amount amount idx
00: 5cb411452a1523a17dba8f4cad71fe120fd693d9a9cd0f0a152e8eef3748e4ea 3.462373917000 1120534 of 0

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": 678653, "vin": [ { "gen": { "height": 678643 } } ], "vout": [ { "amount": 3462373917, "target": { "key": "5cb411452a1523a17dba8f4cad71fe120fd693d9a9cd0f0a152e8eef3748e4ea" } } ], "extra": [ 1, 141, 91, 137, 153, 96, 111, 85, 53, 16, 28, 232, 32, 225, 29, 76, 241, 23, 73, 74, 226, 109, 19, 72, 26, 37, 58, 166, 167, 8, 125, 60, 116, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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