Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f3661da7b297293abe95d96e22181fe958e2faccd5fc48c0fb72dcc6a4bc2d

Tx prefix hash: e79dad18fa2075a843c00cbd364f67359cac8ffd9f0052132810bdaf0ed61bff
Tx public key: 0c0f15ec77d99dc4993d69e98865b51714c3d22acb5e383755839a296ac90132
Timestamp: 1676349426 Timestamp [UCT]: 2023-02-14 04:37:06 Age [y:d:h:m:s]: 02:087:20:30:08
Block: 696558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584404 RingCT/type: yes/0
Extra: 010c0f15ec77d99dc4993d69e98865b51714c3d22acb5e383755839a296ac901320211000000015029cbac000000000000000000

1 output(s) for total of 3.020049834000 dcy

stealth address amount amount idx
00: 43cc0c41b73f8cb79994fb4e84531362e0b8bd80403ad72ec919c5ac3c1ecd4a 3.020049834000 1139587 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": 696568, "vin": [ { "gen": { "height": 696558 } } ], "vout": [ { "amount": 3020049834, "target": { "key": "43cc0c41b73f8cb79994fb4e84531362e0b8bd80403ad72ec919c5ac3c1ecd4a" } } ], "extra": [ 1, 12, 15, 21, 236, 119, 217, 157, 196, 153, 61, 105, 233, 136, 101, 181, 23, 20, 195, 210, 42, 203, 94, 56, 55, 85, 131, 154, 41, 106, 201, 1, 50, 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