Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c8fe0457df2e81250657b6adf2ee635544a0acaf517fe7e88704eaf118b130c

Tx prefix hash: f4a106e6faf430c1cea1f2837d93cb3f2afbc0f93ea4f0d724ed3148ce3799c4
Tx public key: 21c6a032752c529d5064ad3bd2a6b7d9d63ddd6678a146626a9b876bc600e161
Timestamp: 1698696591 Timestamp [UCT]: 2023-10-30 20:09:51 Age [y:d:h:m:s]: 01:144:03:00:28
Block: 881152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363999 RingCT/type: yes/0
Extra: 0121c6a032752c529d5064ad3bd2a6b7d9d63ddd6678a146626a9b876bc600e1610211000000024b8f5122000000000000000000

1 output(s) for total of 0.738546172000 dcy

stealth address amount amount idx
00: 95022cea1a7fdb8783a880d966174673976442262d9766ea17859ad8807799c2 0.738546172000 1336728 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": 881162, "vin": [ { "gen": { "height": 881152 } } ], "vout": [ { "amount": 738546172, "target": { "key": "95022cea1a7fdb8783a880d966174673976442262d9766ea17859ad8807799c2" } } ], "extra": [ 1, 33, 198, 160, 50, 117, 44, 82, 157, 80, 100, 173, 59, 210, 166, 183, 217, 214, 61, 221, 102, 120, 161, 70, 98, 106, 155, 135, 107, 198, 0, 225, 97, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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