Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68db42a05f5c64fa2279f10742f85974055a26f0b396f14a6b24d8d74ff132dc

Tx prefix hash: a7b470382845e64a0655eb43eda8c39ffec6f62bdbee2207570ece88c5a04f6e
Tx public key: 4fb2a8d617ae473a11dd6223ea105c38a9d1cf63caedb2a3a67a87d1565579c9
Timestamp: 1583236136 Timestamp [UCT]: 2020-03-03 11:48:56 Age [y:d:h:m:s]: 04:257:10:15:56
Block: 75399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078422 RingCT/type: yes/0
Extra: 014fb2a8d617ae473a11dd6223ea105c38a9d1cf63caedb2a3a67a87d1565579c902110000000512c4732d000000000000000000

1 output(s) for total of 345.280943766000 dcy

stealth address amount amount idx
00: b5190aaec6c40bc7d22215708b1999a5b717036400ea251a2d3f1e52c49aed27 345.280943766000 139336 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": 75409, "vin": [ { "gen": { "height": 75399 } } ], "vout": [ { "amount": 345280943766, "target": { "key": "b5190aaec6c40bc7d22215708b1999a5b717036400ea251a2d3f1e52c49aed27" } } ], "extra": [ 1, 79, 178, 168, 214, 23, 174, 71, 58, 17, 221, 98, 35, 234, 16, 92, 56, 169, 209, 207, 99, 202, 237, 178, 163, 166, 122, 135, 209, 86, 85, 121, 201, 2, 17, 0, 0, 0, 5, 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