Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b143e7d3c57f1805c853f7e597aa478c729c8997e07d99509c6a1b5eaa6b8413

Tx prefix hash: 2200db70f7396d021ed3637d741e899f971330d9bc5f4e264c7492ff2fb6f6ef
Tx public key: c149d1f7f66f8ee92735d90abca74e0e6c22e1c5f54e2f023a568a1c553f2757
Timestamp: 1703138252 Timestamp [UCT]: 2023-12-21 05:57:32 Age [y:d:h:m:s]: 01:184:06:55:36
Block: 917782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392669 RingCT/type: yes/0
Extra: 01c149d1f7f66f8ee92735d90abca74e0e6c22e1c5f54e2f023a568a1c553f2757021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80aa616419471b7edda52d12c524f9f0eaf9ec516124b3e1ab58bbdc54ef4f72 0.600000000000 1375364 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": 917792, "vin": [ { "gen": { "height": 917782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80aa616419471b7edda52d12c524f9f0eaf9ec516124b3e1ab58bbdc54ef4f72" } } ], "extra": [ 1, 193, 73, 209, 247, 246, 111, 142, 233, 39, 53, 217, 10, 188, 167, 78, 14, 108, 34, 225, 197, 245, 78, 47, 2, 58, 86, 138, 28, 85, 63, 39, 87, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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