Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ba225a06be0ebb62cf53be638d19e1f08098bbbdf437b82f705c013fe708a08

Tx prefix hash: 4265fda3ed06351482da2a593d34ea7ddcbe789a93303d90e956ef01a7a69e0b
Tx public key: 8077339906085c2925c0e3decc34b1f200248e2d2ceac869e5e4de923435c5ae
Timestamp: 1672608181 Timestamp [UCT]: 2023-01-01 21:23:01 Age [y:d:h:m:s]: 02:144:14:13:20
Block: 665517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 625069 RingCT/type: yes/0
Extra: 018077339906085c2925c0e3decc34b1f200248e2d2ceac869e5e4de923435c5ae0211000000015029cbac000000000000000000

1 output(s) for total of 3.827065309000 dcy

stealth address amount amount idx
00: e2e0c7bff53e8782594f006fd622dfdd56d9dee04b38e88a0db12a5d07c114a3 3.827065309000 1106566 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": 665527, "vin": [ { "gen": { "height": 665517 } } ], "vout": [ { "amount": 3827065309, "target": { "key": "e2e0c7bff53e8782594f006fd622dfdd56d9dee04b38e88a0db12a5d07c114a3" } } ], "extra": [ 1, 128, 119, 51, 153, 6, 8, 92, 41, 37, 192, 227, 222, 204, 52, 177, 242, 0, 36, 142, 45, 44, 234, 200, 105, 229, 228, 222, 146, 52, 53, 197, 174, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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