Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c293c9f9eb6d25a3cde7c2c55e0937a872704ed5d2d74cbab32c1dfc8bef928

Tx prefix hash: 267e942ae72647876edf853f2ce538b8cbb66abd95776f9a5b2444ec9e3bb1ca
Tx public key: 589126e8dfe2a9608d60a6b0578178142cb2a2340a4df7736903013ed907dff1
Timestamp: 1580978070 Timestamp [UCT]: 2020-02-06 08:34:30 Age [y:d:h:m:s]: 04:274:03:54:15
Block: 59766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087311 RingCT/type: yes/0
Extra: 01589126e8dfe2a9608d60a6b0578178142cb2a2340a4df7736903013ed907dff1021100000004724f989b000000000000000000

1 output(s) for total of 389.019391884000 dcy

stealth address amount amount idx
00: a91bdd3d2aea0b716e12f54df729e1fd1adc1635ea27a5149f7f6ee40976dcd2 389.019391884000 110270 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": 59776, "vin": [ { "gen": { "height": 59766 } } ], "vout": [ { "amount": 389019391884, "target": { "key": "a91bdd3d2aea0b716e12f54df729e1fd1adc1635ea27a5149f7f6ee40976dcd2" } } ], "extra": [ 1, 88, 145, 38, 232, 223, 226, 169, 96, 141, 96, 166, 176, 87, 129, 120, 20, 44, 178, 162, 52, 10, 77, 247, 115, 105, 3, 1, 62, 217, 7, 223, 241, 2, 17, 0, 0, 0, 4, 114, 79, 152, 155, 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