Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24d3400d159fc36fca8215beba4f110ef8a299fc2234e70b333ecac1eec28062

Tx prefix hash: de3aeac8e33f2b2ca711f72978a5f83f99563ee8bc7be94be5f166f473d5d25b
Tx public key: bb34c465dc74a4e7cc14733a9bbe2eaafac5c83b983f6c7b49859e520f8df555
Timestamp: 1732986222 Timestamp [UCT]: 2024-11-30 17:03:42 Age [y:d:h:m:s]: 00:130:10:30:52
Block: 1165120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93032 RingCT/type: yes/0
Extra: 01bb34c465dc74a4e7cc14733a9bbe2eaafac5c83b983f6c7b49859e520f8df555021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c07af760841042d53fb8ddd48e42387efff1379d1d6d02b200bb50be48992252 0.600000000000 1650795 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": 1165130, "vin": [ { "gen": { "height": 1165120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c07af760841042d53fb8ddd48e42387efff1379d1d6d02b200bb50be48992252" } } ], "extra": [ 1, 187, 52, 196, 101, 220, 116, 164, 231, 204, 20, 115, 58, 155, 190, 46, 170, 250, 197, 200, 59, 152, 63, 108, 123, 73, 133, 158, 82, 15, 141, 245, 85, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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