Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83b4af08569f0374eff0dc6bf46e87f417a8da564ebe1aca1f54daa006a6c951

Tx prefix hash: e77373a7ab682f48e78e7b816b0a2f3cf99c60f02b2466f9c85de5500c17eb18
Tx public key: e2565d48734e6ec8b9609e1b2272db7c97e96d659cc8bffc3a18c67aa8805962
Timestamp: 1722027615 Timestamp [UCT]: 2024-07-26 21:00:15 Age [y:d:h:m:s]: 00:301:20:23:03
Block: 1074357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215684 RingCT/type: yes/0
Extra: 01e2565d48734e6ec8b9609e1b2272db7c97e96d659cc8bffc3a18c67aa8805962021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17c4f6320a0d0bcd540b1d8879638eaf20a38f79100d639d124cb46d766cfa96 0.600000000000 1546870 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": 1074367, "vin": [ { "gen": { "height": 1074357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17c4f6320a0d0bcd540b1d8879638eaf20a38f79100d639d124cb46d766cfa96" } } ], "extra": [ 1, 226, 86, 93, 72, 115, 78, 110, 200, 185, 96, 158, 27, 34, 114, 219, 124, 151, 233, 109, 101, 156, 200, 191, 252, 58, 24, 198, 122, 168, 128, 89, 98, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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