Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b835707143fd0faf33b4f2ab9a11361a18fc75e0c5689ac79ddb9f774d5e9446

Tx prefix hash: 2f9e4429c3bffb2edbcd2f16e33d543be01470b50cbc820341afbbf8962a2122
Tx public key: 0e70aa26910096f3b7e485af47a719b349d52e13d19492fae317c9f7ca1514f3
Timestamp: 1583239704 Timestamp [UCT]: 2020-03-03 12:48:24 Age [y:d:h:m:s]: 04:364:03:07:49
Block: 75743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154162 RingCT/type: yes/0
Extra: 010e70aa26910096f3b7e485af47a719b349d52e13d19492fae317c9f7ca1514f302110000006203d36d11000000000000000000

1 output(s) for total of 344.375934554000 dcy

stealth address amount amount idx
00: 285ac2377a8086e59fcd8e23a822fee071b0bb9ebd41e87c07bdb6a2a6ea8f47 344.375934554000 139713 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": 75753, "vin": [ { "gen": { "height": 75743 } } ], "vout": [ { "amount": 344375934554, "target": { "key": "285ac2377a8086e59fcd8e23a822fee071b0bb9ebd41e87c07bdb6a2a6ea8f47" } } ], "extra": [ 1, 14, 112, 170, 38, 145, 0, 150, 243, 183, 228, 133, 175, 71, 167, 25, 179, 73, 213, 46, 19, 209, 148, 146, 250, 227, 23, 201, 247, 202, 21, 20, 243, 2, 17, 0, 0, 0, 98, 3, 211, 109, 17, 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