Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d950c6405d4fba054cfefe561c0deada318d8d78ce5d400c4a25eccda280c8b

Tx prefix hash: 8532ee65a7b6c0f8c64e7d978002292f7e9230d8482a86d980f09315f103f857
Tx public key: c9e00b0d1f78c978b660dd0a61777b2b5c2d60a95063ca3aa1e9607a9716f888
Timestamp: 1576424348 Timestamp [UCT]: 2019-12-15 15:39:08 Age [y:d:h:m:s]: 05:080:14:59:24
Block: 27328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204449 RingCT/type: yes/0
Extra: 01c9e00b0d1f78c978b660dd0a61777b2b5c2d60a95063ca3aa1e9607a9716f88802110000002b9159db1e000000000000000000

1 output(s) for total of 498.255220573000 dcy

stealth address amount amount idx
00: 2d49b2e891d928af8de7159994be701be4dbd9865dcbdcb38ff49546a700c204 498.255220573000 45324 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": 27338, "vin": [ { "gen": { "height": 27328 } } ], "vout": [ { "amount": 498255220573, "target": { "key": "2d49b2e891d928af8de7159994be701be4dbd9865dcbdcb38ff49546a700c204" } } ], "extra": [ 1, 201, 224, 11, 13, 31, 120, 201, 120, 182, 96, 221, 10, 97, 119, 123, 43, 92, 45, 96, 169, 80, 99, 202, 58, 161, 233, 96, 122, 151, 22, 248, 136, 2, 17, 0, 0, 0, 43, 145, 89, 219, 30, 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