Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9bba770d5ab18aaa6e5fb66f64557da218cdd4d5ad777f0a91e0ae99e9f5f32

Tx prefix hash: 478dce07b94b530d87a2c71707c8e3f593269bdc82444c82d3099bf92c4fabec
Tx public key: 6a7038979a93ed33e33f4f7df09c830e666fbe3f402dbe3b62a93c6d772c7f3a
Timestamp: 1708001105 Timestamp [UCT]: 2024-02-15 12:45:05 Age [y:d:h:m:s]: 01:044:18:32:44
Block: 958067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293038 RingCT/type: yes/0
Extra: 016a7038979a93ed33e33f4f7df09c830e666fbe3f402dbe3b62a93c6d772c7f3a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b547fe62c49ad91ce93c299bc74aed86e115eefdc6d8c9f84f17fbcd2cae9dac 0.600000000000 1417420 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": 958077, "vin": [ { "gen": { "height": 958067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b547fe62c49ad91ce93c299bc74aed86e115eefdc6d8c9f84f17fbcd2cae9dac" } } ], "extra": [ 1, 106, 112, 56, 151, 154, 147, 237, 51, 227, 63, 79, 125, 240, 156, 131, 14, 102, 111, 190, 63, 64, 45, 190, 59, 98, 169, 60, 109, 119, 44, 127, 58, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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