Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1878d4934ef45fd819bd4195a570aeab542900bca9fb84b2400fb1cb032aec7c

Tx prefix hash: b5e985a6e2be85be5af54cf6713a6ee56b3eca4ac4c388d1af927f024f696cb3
Tx public key: 59c89ac1f262ccc4a99b51e9dcbd8789b1c25e19454b9a0c4c741cfe01586137
Timestamp: 1577024792 Timestamp [UCT]: 2019-12-22 14:26:32 Age [y:d:h:m:s]: 05:073:13:15:07
Block: 29653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202032 RingCT/type: yes/0
Extra: 0159c89ac1f262ccc4a99b51e9dcbd8789b1c25e19454b9a0c4c741cfe015861370211000000218a2ee0d9000000000000000000

1 output(s) for total of 489.494892062000 dcy

stealth address amount amount idx
00: e9c2c1d722566474e1a815103f65d299a68a39c997f99bcfb146b6a353c9bcb2 489.494892062000 48799 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": 29663, "vin": [ { "gen": { "height": 29653 } } ], "vout": [ { "amount": 489494892062, "target": { "key": "e9c2c1d722566474e1a815103f65d299a68a39c997f99bcfb146b6a353c9bcb2" } } ], "extra": [ 1, 89, 200, 154, 193, 242, 98, 204, 196, 169, 155, 81, 233, 220, 189, 135, 137, 177, 194, 94, 25, 69, 75, 154, 12, 76, 116, 28, 254, 1, 88, 97, 55, 2, 17, 0, 0, 0, 33, 138, 46, 224, 217, 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