Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf07f448a00762941ef1e7d1adf66a3b04a383ea67a379c1587b6774d88521e

Tx prefix hash: 229cfb763a78e8be11b97137d9fb108c344b6bf6098f475ca0b9119f09109b06
Tx public key: b338a03547fb8ebbf897e0ce31f5d756e12254f98cbe88e54babbb37f4af087f
Timestamp: 1575883088 Timestamp [UCT]: 2019-12-09 09:18:08 Age [y:d:h:m:s]: 05:021:13:03:42
Block: 24001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161302 RingCT/type: yes/0
Extra: 01b338a03547fb8ebbf897e0ce31f5d756e12254f98cbe88e54babbb37f4af087f02110000001e9159db1e000000000000000000

1 output(s) for total of 511.064358926000 dcy

stealth address amount amount idx
00: baf07f7c18e127a552cbee264ae3cbc81fa64d8c83e91ef0fe934405d9dee8d4 511.064358926000 38902 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": 24011, "vin": [ { "gen": { "height": 24001 } } ], "vout": [ { "amount": 511064358926, "target": { "key": "baf07f7c18e127a552cbee264ae3cbc81fa64d8c83e91ef0fe934405d9dee8d4" } } ], "extra": [ 1, 179, 56, 160, 53, 71, 251, 142, 187, 248, 151, 224, 206, 49, 245, 215, 86, 225, 34, 84, 249, 140, 190, 136, 229, 75, 171, 187, 55, 244, 175, 8, 127, 2, 17, 0, 0, 0, 30, 145, 89, 219, 30, 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