Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaf02a14e3536f4ad73723f523397f5cc5eb5334cc13033d84d101b205a039dd

Tx prefix hash: 47298a3586d2972d4f697f96362bdeef2cec6d7fdf3de569b5a672275dd4126c
Tx public key: 9d9f3a03b0545d6b1a8b2f72bfcba78c661fbb15334b7b22fe1936c42a0cd599
Timestamp: 1580888595 Timestamp [UCT]: 2020-02-05 07:43:15 Age [y:d:h:m:s]: 04:328:12:47:26
Block: 59048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126196 RingCT/type: yes/0
Extra: 019d9f3a03b0545d6b1a8b2f72bfcba78c661fbb15334b7b22fe1936c42a0cd59902110000000417786bcf000000000000000000

1 output(s) for total of 391.156258847000 dcy

stealth address amount amount idx
00: 4e2f350cb7282c73c09b0e3437b727b319d47bb1cfcb3a6d8d356b55f4e3db27 391.156258847000 109037 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": 59058, "vin": [ { "gen": { "height": 59048 } } ], "vout": [ { "amount": 391156258847, "target": { "key": "4e2f350cb7282c73c09b0e3437b727b319d47bb1cfcb3a6d8d356b55f4e3db27" } } ], "extra": [ 1, 157, 159, 58, 3, 176, 84, 93, 107, 26, 139, 47, 114, 191, 203, 167, 140, 102, 31, 187, 21, 51, 75, 123, 34, 254, 25, 54, 196, 42, 12, 213, 153, 2, 17, 0, 0, 0, 4, 23, 120, 107, 207, 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