Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29b8c2e4c114d9165c00a232f5d82ac07b982100432984ca58f62a622a6d62e1

Tx prefix hash: a3ccc3d1857dbfb42e3af21633c5566edb14fc0448434d45dad7b4a847b0f983
Tx public key: 5862b1a1012b5222b2aef52e5db82e43da29b5d797f008333c53bb72e501f001
Timestamp: 1737982090 Timestamp [UCT]: 2025-01-27 12:48:10 Age [y:d:h:m:s]: 00:046:03:10:50
Block: 1206243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32987 RingCT/type: yes/0
Extra: 015862b1a1012b5222b2aef52e5db82e43da29b5d797f008333c53bb72e501f0010211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6fa9b3db7bd921c7c0b2faf723148f194774f842c8c070a8f52a3c6e830543b 0.600000000000 1692946 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": 1206253, "vin": [ { "gen": { "height": 1206243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6fa9b3db7bd921c7c0b2faf723148f194774f842c8c070a8f52a3c6e830543b" } } ], "extra": [ 1, 88, 98, 177, 161, 1, 43, 82, 34, 178, 174, 245, 46, 93, 184, 46, 67, 218, 41, 181, 215, 151, 240, 8, 51, 60, 83, 187, 114, 229, 1, 240, 1, 2, 17, 0, 0, 0, 7, 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