Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 943184b731543e31594bea0cbc5c2a71cc321a8d25b18ca23d9660ffb312fcd9

Tx prefix hash: 28b36d1ad9499e39352effd6a503670b3d4dfd7a77f29ffa832a3f7bee3ce1ed
Tx public key: 46d870c93a53b519b61d3495a58275274071ac19f8b9e99179315e1bf0ca7d73
Timestamp: 1663190930 Timestamp [UCT]: 2022-09-14 21:28:50 Age [y:d:h:m:s]: 02:062:15:42:24
Block: 588030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566232 RingCT/type: yes/0
Extra: 0146d870c93a53b519b61d3495a58275274071ac19f8b9e99179315e1bf0ca7d73021100000001143619d6000000000000000000

1 output(s) for total of 6.912140920000 dcy

stealth address amount amount idx
00: db4118d6ba5936516bd43bfdae318128eec3dd9f809ea4be40a92e9002fedc50 6.912140920000 1022227 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": 588040, "vin": [ { "gen": { "height": 588030 } } ], "vout": [ { "amount": 6912140920, "target": { "key": "db4118d6ba5936516bd43bfdae318128eec3dd9f809ea4be40a92e9002fedc50" } } ], "extra": [ 1, 70, 216, 112, 201, 58, 83, 181, 25, 182, 29, 52, 149, 165, 130, 117, 39, 64, 113, 172, 25, 248, 185, 233, 145, 121, 49, 94, 27, 240, 202, 125, 115, 2, 17, 0, 0, 0, 1, 20, 54, 25, 214, 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