Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a43561c3d3bf50050114906c7df8b0107db3086f5790c128694215df911c16f1

Tx prefix hash: c2eeaf90f386e389b8e5b9da285e7962125ea6cedf1fd380ad6ff16f6e1cf361
Tx public key: d8b712f48a96924d770c4998f3a40a485b9dc288e82300b831138f17f86808d2
Timestamp: 1685095663 Timestamp [UCT]: 2023-05-26 10:07:43 Age [y:d:h:m:s]: 01:357:10:59:45
Block: 768429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516705 RingCT/type: yes/0
Extra: 01d8b712f48a96924d770c4998f3a40a485b9dc288e82300b831138f17f86808d202110000000375e3f0e9000000000000000000

1 output(s) for total of 1.745323391000 dcy

stealth address amount amount idx
00: e185597d3eb8ae546a29ea990b54629aa7f721fe6f0d3a0da03afb463d22e48f 1.745323391000 1217624 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": 768439, "vin": [ { "gen": { "height": 768429 } } ], "vout": [ { "amount": 1745323391, "target": { "key": "e185597d3eb8ae546a29ea990b54629aa7f721fe6f0d3a0da03afb463d22e48f" } } ], "extra": [ 1, 216, 183, 18, 244, 138, 150, 146, 77, 119, 12, 73, 152, 243, 164, 10, 72, 91, 157, 194, 136, 232, 35, 0, 184, 49, 19, 143, 23, 248, 104, 8, 210, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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