Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16b9e8ba779605075f9a75068deea790539360a27575376c5e23bd9914ca55b1

Tx prefix hash: 38234f3bc3e1f5dc5b51a353dc5437acf31f6cf36d6044ecad6c122adf02e3d1
Tx public key: a7f94d6bf3d9150f933e07314aba1f35182e4bad242976dd8035d596df04e2d9
Timestamp: 1581822331 Timestamp [UCT]: 2020-02-16 03:05:31 Age [y:d:h:m:s]: 05:283:22:23:56
Block: 65809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1353686 RingCT/type: yes/0
Extra: 01a7f94d6bf3d9150f933e07314aba1f35182e4bad242976dd8035d596df04e2d902110000000212c4732d000000000000000000

1 output(s) for total of 371.490980755000 dcy

stealth address amount amount idx
00: 7a5d7bc0a65c1dbd2a34fadb1eafd8f17c4afd78d567a892c03d18de9d335c86 371.490980755000 121412 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": 65819, "vin": [ { "gen": { "height": 65809 } } ], "vout": [ { "amount": 371490980755, "target": { "key": "7a5d7bc0a65c1dbd2a34fadb1eafd8f17c4afd78d567a892c03d18de9d335c86" } } ], "extra": [ 1, 167, 249, 77, 107, 243, 217, 21, 15, 147, 62, 7, 49, 74, 186, 31, 53, 24, 46, 75, 173, 36, 41, 118, 221, 128, 53, 213, 150, 223, 4, 226, 217, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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