Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87f5954f818a75a293b39e00addcfb6f46520a829e78335ba42533ab8e550c1

Tx prefix hash: 6cea05f63a3d0374ca57db3fc651964a67fe9643ffa1d1cfb0eda4fb02e3bb41
Tx public key: aed0f7a0ddd67575ad52fec7eea9a72105f8c8c047b1430dedeb4dd6a2a0b694
Timestamp: 1700614819 Timestamp [UCT]: 2023-11-22 01:00:19 Age [y:d:h:m:s]: 01:141:21:54:07
Block: 896843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362603 RingCT/type: yes/0
Extra: 01aed0f7a0ddd67575ad52fec7eea9a72105f8c8c047b1430dedeb4dd6a2a0b6940211000000054b8f5122000000000000000000

1 output(s) for total of 0.655219527000 dcy

stealth address amount amount idx
00: 16eacf98b860accff3c6d73223bf5031b63323b51370b16bc6514712ee80530e 0.655219527000 1353186 of 0

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": 896853, "vin": [ { "gen": { "height": 896843 } } ], "vout": [ { "amount": 655219527, "target": { "key": "16eacf98b860accff3c6d73223bf5031b63323b51370b16bc6514712ee80530e" } } ], "extra": [ 1, 174, 208, 247, 160, 221, 214, 117, 117, 173, 82, 254, 199, 238, 169, 167, 33, 5, 248, 200, 192, 71, 177, 67, 13, 237, 235, 77, 214, 162, 160, 182, 148, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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