Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a58ec63ed7bad2bb3975e4af2312286f59f9d57e696b57e2358877f7c325f9b3

Tx prefix hash: 9122eefef68f06e1fbc459474daa7094fa5d98010e51e46b79064b895e65512a
Tx public key: 840c321e7c684e4e1b67058592cb7112f5f0043082dbe1235acd62f38facc4c8
Timestamp: 1580570999 Timestamp [UCT]: 2020-02-01 15:29:59 Age [y:d:h:m:s]: 05:076:14:39:37
Block: 56709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1206525 RingCT/type: yes/0
Extra: 01840c321e7c684e4e1b67058592cb7112f5f0043082dbe1235acd62f38facc4c80211000000028a2ee0d9000000000000000000

1 output(s) for total of 398.199183452000 dcy

stealth address amount amount idx
00: f0f3d56ceb6eb485bb7d218aaf18789db6dd92463a9e3154d4d339b346ea3f76 398.199183452000 104510 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": 56719, "vin": [ { "gen": { "height": 56709 } } ], "vout": [ { "amount": 398199183452, "target": { "key": "f0f3d56ceb6eb485bb7d218aaf18789db6dd92463a9e3154d4d339b346ea3f76" } } ], "extra": [ 1, 132, 12, 50, 30, 124, 104, 78, 78, 27, 103, 5, 133, 146, 203, 113, 18, 245, 240, 4, 48, 130, 219, 225, 35, 90, 205, 98, 243, 143, 172, 196, 200, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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