Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1477f7b2eed1726b1883583d4a7fbdf539f82da94c0183d60c3144523a9a499

Tx prefix hash: 331e38d6623463d8baee5ba73d0a6823a6ae3a5b9f1730b9f7ea55b47276f138
Tx public key: 98b1b55c7c2d705e37d2ef87513226e8b1cb98f5d670d57b91609253298a21ca
Timestamp: 1637319095 Timestamp [UCT]: 2021-11-19 10:51:35 Age [y:d:h:m:s]: 03:347:06:43:56
Block: 377547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1024535 RingCT/type: yes/0
Extra: 0198b1b55c7c2d705e37d2ef87513226e8b1cb98f5d670d57b91609253298a21ca021100000002b494d89c000000000000000000

1 output(s) for total of 34.438607218000 dcy

stealth address amount amount idx
00: 1f88757b056e3e0a723f4e339566238a74c0e4ef32a845d8ce454b9d6e87c210 34.438607218000 763631 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": 377557, "vin": [ { "gen": { "height": 377547 } } ], "vout": [ { "amount": 34438607218, "target": { "key": "1f88757b056e3e0a723f4e339566238a74c0e4ef32a845d8ce454b9d6e87c210" } } ], "extra": [ 1, 152, 177, 181, 92, 124, 45, 112, 94, 55, 210, 239, 135, 81, 50, 38, 232, 177, 203, 152, 245, 214, 112, 213, 123, 145, 96, 146, 83, 41, 138, 33, 202, 2, 17, 0, 0, 0, 2, 180, 148, 216, 156, 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