Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa2b32ed145c48782c06ba889b8ea67ef857ed7f41259f64922f2b5cb8f623f0

Tx prefix hash: 3e7d596d8f5e283af56935224fdad65194761d7bc3786b3c519462eaa4154648
Tx public key: a2568a154fc5df4c94fbcaa6a340518bde07a145389dffd96d91594bf9898a5d
Timestamp: 1722820150 Timestamp [UCT]: 2024-08-05 01:09:10 Age [y:d:h:m:s]: 00:251:05:31:05
Block: 1080926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179456 RingCT/type: yes/0
Extra: 01a2568a154fc5df4c94fbcaa6a340518bde07a145389dffd96d91594bf9898a5d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bebc9d7d433f5c462de3a8b136009d9b0fa2ef052cad73a422445c182ab2be4f 0.600000000000 1554477 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": 1080936, "vin": [ { "gen": { "height": 1080926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bebc9d7d433f5c462de3a8b136009d9b0fa2ef052cad73a422445c182ab2be4f" } } ], "extra": [ 1, 162, 86, 138, 21, 79, 197, 223, 76, 148, 251, 202, 166, 163, 64, 81, 139, 222, 7, 161, 69, 56, 157, 255, 217, 109, 145, 89, 75, 249, 137, 138, 93, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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