Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 871d8955e073d03d302092079f8543f663bfb85a371b32eb062d826d295e3638

Tx prefix hash: 21ef6a2202d22c4ff63cf2f6fcc02e0e4fd18e31401b40e4b7583fc61fa6f0ab
Tx public key: ceebacd1ebc055cda4634543b9f3ae91fb47c2f574b2afabab77259b0cc35a17
Timestamp: 1740967868 Timestamp [UCT]: 2025-03-03 02:11:08 Age [y:d:h:m:s]: 00:263:21:11:49
Block: 1230928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186345 RingCT/type: yes/0
Extra: 01ceebacd1ebc055cda4634543b9f3ae91fb47c2f574b2afabab77259b0cc35a170211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd74557b92dd1f8d9cc7572ae3cfd67d4f0dc68277a90bc3d5ce050bdc46c074 0.600000000000 1717831 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": 1230938, "vin": [ { "gen": { "height": 1230928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd74557b92dd1f8d9cc7572ae3cfd67d4f0dc68277a90bc3d5ce050bdc46c074" } } ], "extra": [ 1, 206, 235, 172, 209, 235, 192, 85, 205, 164, 99, 69, 67, 185, 243, 174, 145, 251, 71, 194, 245, 116, 178, 175, 171, 171, 119, 37, 155, 12, 195, 90, 23, 2, 17, 0, 0, 0, 4, 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