Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a45075411d66a9fb32d187aac328f5a7faf0498ee0586fae7d83f6eec669422c

Tx prefix hash: 55743798041316a6e7d248724e7766e3b37ac3d39ec7de824c154428bb872fa5
Tx public key: 5dfc1f5c76e07e0dcef4dee8f25294e066218c838250e2d65d6c897fa9e17447
Timestamp: 1736132188 Timestamp [UCT]: 2025-01-06 02:56:28 Age [y:d:h:m:s]: 00:093:14:23:49
Block: 1191168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66671 RingCT/type: yes/0
Extra: 015dfc1f5c76e07e0dcef4dee8f25294e066218c838250e2d65d6c897fa9e174470211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed90a0ab1de386fc8623e67f57549db54136b24968481160a03d9c6ccda08300 0.600000000000 1677691 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": 1191178, "vin": [ { "gen": { "height": 1191168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed90a0ab1de386fc8623e67f57549db54136b24968481160a03d9c6ccda08300" } } ], "extra": [ 1, 93, 252, 31, 92, 118, 224, 126, 13, 206, 244, 222, 232, 242, 82, 148, 224, 102, 33, 140, 131, 130, 80, 226, 214, 93, 108, 137, 127, 169, 225, 116, 71, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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