Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77d5b09c35d00a2012afde7ef699c5ed5bd08a08029ff94f66c4d7e776271485

Tx prefix hash: 4a1df5ad0e89752a79c49642247817e1c6a2498aaa9bc5fff4ffda6ee4785ac2
Tx public key: 1061c92f7fb6ef3a550d394de842f2b526977d588f3747d18b1b78989d787237
Timestamp: 1580705503 Timestamp [UCT]: 2020-02-03 04:51:43 Age [y:d:h:m:s]: 05:272:01:36:44
Block: 57778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1343975 RingCT/type: yes/0
Extra: 011061c92f7fb6ef3a550d394de842f2b526977d588f3747d18b1b78989d7872370211000000064943cd9f000000000000000000

1 output(s) for total of 394.971556868000 dcy

stealth address amount amount idx
00: 3533943f460402388e6e0db0a45a5742c75c1dc2b68c27472c1b98f1b1636a77 394.971556868000 106770 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": 57788, "vin": [ { "gen": { "height": 57778 } } ], "vout": [ { "amount": 394971556868, "target": { "key": "3533943f460402388e6e0db0a45a5742c75c1dc2b68c27472c1b98f1b1636a77" } } ], "extra": [ 1, 16, 97, 201, 47, 127, 182, 239, 58, 85, 13, 57, 77, 232, 66, 242, 181, 38, 151, 125, 88, 143, 55, 71, 209, 139, 27, 120, 152, 157, 120, 114, 55, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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