Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f51d68a7536c89cc5592314840758d9418bbd946fa545f1bdf19fd7c8fd93261

Tx prefix hash: 6190769f1db72bf3fd208833b90f318ef086d83ab7fbef23c22d4f2075625cea
Tx public key: c426845715a3910bfb1ab5b01c084d5527b32e7e5811f9eed99270559b1fcb72
Timestamp: 1577727503 Timestamp [UCT]: 2019-12-30 17:38:23 Age [y:d:h:m:s]: 05:111:00:21:33
Block: 35196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1229109 RingCT/type: yes/0
Extra: 01c426845715a3910bfb1ab5b01c084d5527b32e7e5811f9eed99270559b1fcb720211000000024ac5aa02000000000000000000

1 output(s) for total of 469.312773708000 dcy

stealth address amount amount idx
00: feb550994ac3ca38cecf513ae4b8c63a853df154521c237070006dbe7a0a296e 469.312773708000 59276 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": 35206, "vin": [ { "gen": { "height": 35196 } } ], "vout": [ { "amount": 469312773708, "target": { "key": "feb550994ac3ca38cecf513ae4b8c63a853df154521c237070006dbe7a0a296e" } } ], "extra": [ 1, 196, 38, 132, 87, 21, 163, 145, 11, 251, 26, 181, 176, 28, 8, 77, 85, 39, 179, 46, 126, 88, 17, 249, 238, 217, 146, 112, 85, 155, 31, 203, 114, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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