Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c6f5f789ee8e8286af4388f4ba99d6c446d69e9bd5f719d1775a04d29790433

Tx prefix hash: 521e3e8d87d7c4b27a5a213116137800d43a869ea8ecbf975608a1eff048364c
Tx public key: 43ce1e53ab13d27bded64b3b05cc4e0dcf2e1f915fd36b475101604a9f2a22ba
Timestamp: 1737222776 Timestamp [UCT]: 2025-01-18 17:52:56 Age [y:d:h:m:s]: 00:153:19:41:53
Block: 1200160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109628 RingCT/type: yes/0
Extra: 0143ce1e53ab13d27bded64b3b05cc4e0dcf2e1f915fd36b475101604a9f2a22ba0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8e5ad72d1134a16107660939778d7ee138490b2dd3db96a0757c3996b62db4b 0.600000000000 1686801 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": 1200170, "vin": [ { "gen": { "height": 1200160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8e5ad72d1134a16107660939778d7ee138490b2dd3db96a0757c3996b62db4b" } } ], "extra": [ 1, 67, 206, 30, 83, 171, 19, 210, 123, 222, 214, 75, 59, 5, 204, 78, 13, 207, 46, 31, 145, 95, 211, 107, 71, 81, 1, 96, 74, 159, 42, 34, 186, 2, 17, 0, 0, 0, 1, 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